Skip to content

Clarify that scoped contexts on @type use the term used #632

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 12, 2018
Merged

Conversation

gkellogg
Copy link
Member

rather than it's expanded IRI, to find a scoped context.

Fixes #521.

…n it's expanded IRI, to find a scoped context.

Fixes #521.
@gkellogg gkellogg requested a review from azaroth42 April 12, 2018 19:26
@gkellogg
Copy link
Member Author

Rob, please consider if the added wording clarifies this for you; it could probably be word-smithed more.

<p>When expanding, each value of <code>@type</code> is considered
(ordering them lexographically) where that value is also a <a>term</a> in
the <a>active context</a> having its own <a>context</a>. If so, that
<a>context</a> as applied to the <a>active context</a>. When compacting, if
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

s/as/is/ I believe


<p>When expanding, each value of <code>@type</code> is considered
(ordering them lexographically) where that value is also a <a>term</a> in
the <a>active context</a> having its own <a>context</a>. If so, that
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

having its own ... subsidiary? embedded? something? ... context.

@azaroth42
Copy link
Contributor

Looks good overall. One typo, one minor note about clarity of wording -- I think an adjective to distinguish the scoped context of the term would help understanding.

@gkellogg gkellogg merged commit 35e0771 into master Apr 12, 2018
@gkellogg gkellogg deleted the issue-521 branch April 12, 2018 20:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants